Conversation
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
View your CI Pipeline Execution ↗ for commit 56f7424
☁️ Nx Cloud last updated this comment at |
jaysoo
enabled auto-merge (squash)
August 7, 2026 00:57
jaysoo
disabled auto-merge
August 7, 2026 01:05
Page sat under Adopting Nx as a config/command mapping table with one
"run nx init" example. Claimed nx init output was wrong: `dev` gets
`{ "cache": false }`, not `{ "continuous": true }` - the converter drops
`persistent`.
Moved to the knowledge base at /docs/kb/from-turborepo (redirect added) and
featured; "Nx and Angular Versions" unfeatured to make room.
8 numbered steps + AI prompt card at top. Covers what `nx init` does not
convert: `<package>#<task>` fragments, per-package turbo.json, `persistent`,
task-level `env`, top-level keys like `ui`. Fragments map to the
`targetDefaults` array form with `filter.projects`. Mapping tables demoted to
additional considerations.
Steps and prompt validated by running the copy-prompt end to end against three
generated turborepo fixtures. Fixes found that way:
- `sharedGlobals` caveat. `nx init` reaches it via `default`, so any target
with an explicit `inputs` array bypasses it and `globalEnv` /
`globalDependencies` stop invalidating that target.
- Filtered `targetDefaults` entries replace baseline values per key, arrays
included, so filtered `inputs` must re-list the baseline.
- Per-package turbo.json now has a stated port path, not just a delete step.
- Directory patterns over name globs for shared rules; tags are set in project
config, which the page never said.
- Cleanup sweeps the whole workspace, not just root scripts - `turbo gen` in a
package and `eslint-plugin-turbo` both survived a literal pass.
DOC-571
## Current Behavior Intro paragraph forward-referenced step numbers and read as part of the AI prompt card. Merge-semantics prose in step 3 was dense. Cleanup sweep was unix-only. Wording implied Nx suits large workspaces and turbo small ones. ## Expected Behavior Intro trimmed to one paragraph. Step 3 resolution rules cut to two bullets plus a link to the target defaults reference. grep sweep gets a PowerShell tab. CI section reframed around what a cache cannot help with. Also applied the updated STYLE_GUIDE anti-AI rules: dropped significance clauses and reverse drama beats. 99 words shorter. ## Related Issue(s) DOC-571
## Current Behavior Step 3 spent a paragraph and two bullets on override resolution, repeated the array explanation on both sides of the code block, and carried a second code block that differed by one line. sharedGlobals aside showed the target inputs without the namedInputs block it refers to. ## Expected Behavior One sentence for the array shape, one for the override rule, rest to the reference. Second code block folded into prose. sharedGlobals aside shows the namedInputs entry alongside the target. ## Related Issue(s) DOC-571
## Current Behavior
Paragraphs opened with a short label sentence ("CI is the other gap.",
"Two smaller differences.", "Nx uses the flag for more than bookkeeping.")
before the content that carried the actual claim.
## Expected Behavior
Labels removed or folded into the sentence that follows. Content unchanged.
## Related Issue(s)
DOC-571
## Current Behavior A paragraph that opens with a short label sentence passes the drama-beat test, because the sentences after it do add facts. Nothing else covers it. ## Expected Behavior New "Cut signpost openers" rule, plus a first-sentence read in the pre-publish pass order. ## Related Issue(s) DOC-571
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current Behavior
The Turborepo migration page was a config and command mapping table with a single
nx initexample, and it documentednx initoutput that never existed (devcomes out as{ "cache": false }, not{ "continuous": true }).Expected Behavior
Eight numbered steps with an AI prompt card, covering what
nx initdoes not convert. Moved to/docs/kb/from-turborepoand featured, with a redirect. Steps and prompt were validated by running the copy-prompt end to end against three generated Turborepo fixtures.Preview: https://deploy-preview-36594--nx-docs.netlify.app/docs/kb/from-turborepo
Related Issue(s)
DOC-571